Looking at this I still think that this could be CLI tools, doesn't look to complicated. I think one tool per endpoint would be a simpler start.

Also I think we should add some pre-defined convenient constants for the EIC codes which gives DeliveryArea objects.

If you aim for merging this notebook:

• the notebook should be in an example folder on top level
• GRIDPOOL_ID can be a constant in the notebook set to some dummy value
• Remove the cell output

Does the client also offer a way to retrieve a list of public trades and continue streaming all subsequent trades?

GRIDPOOL_ID can be a constant in the notebook set to some dummy value

Even if this would make the notebook fail?

Looking at this I still think that this could be CLI tools, doesn't look to complicated. I think one tool per endpoint would be a simpler start.

Ok noted. Should we still merge this or rather not?

Even if this would make the notebook fail?

Good point, not sure, could also be a single env file that sets variables read from environment. However,

Should we still merge this or rather not?

Do you think it's useful?

However,

I recon part of your message is missing here?

Do you think it's useful?

Yea I'd say that for some clients it would be great to have.

Yea I'd say that for some clients it would be great to have.

The problem I see with having examples and this notebook is to maintain both, former is not such a big problem but notebooks are not so nice to maintain. So I would only keep it if it has some benefits over the CLI tools, e.g. I think it can be good for documenting examples. But the current version is not really complete yet.

notebooks are not so nice to maintain

True that's a good point. I won't merge this then. I started working on the CLI tools & am almost done. I'll create a new PR for it tonight or tomorrow.